NTISthis.com

Evidence Guide: ICTSAS503 - Perform systems tests

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTSAS503 - Perform systems tests

What evidence can you provide to prove your understanding of each of the following citeria?

Prepare for test

  1. Prepare test environment
  2. Determine software life cycle
  3. Define test plan and appropriate test tools
  4. Recognise and separate the system into runnable modules that mirror live scenarios
  5. Gather and prepare logs and result sheets
  6. Notify operations of scheduled test to ensure preparedness and understanding of implications for operations
  7. Test scripts for online test or test run for batch test
  8. Conduct walk-through to review expected results against acceptance criteria and system requirements documentation
Prepare test environment

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine software life cycle

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Define test plan and appropriate test tools

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Recognise and separate the system into runnable modules that mirror live scenarios

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Gather and prepare logs and result sheets

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Notify operations of scheduled test to ensure preparedness and understanding of implications for operations

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Test scripts for online test or test run for batch test

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Conduct walk-through to review expected results against acceptance criteria and system requirements documentation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Conduct test

  1. Run test scripts and document results according to test and acceptance processes
  2. Perform required quality benchmarks or comparisons for acceptance testing
  3. Adopt organisation and industry standards
  4. Compare actual results to expected results on completion of each system unit, and complete result sheets
Run test scripts and document results according to test and acceptance processes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Perform required quality benchmarks or comparisons for acceptance testing

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Adopt organisation and industry standards

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Compare actual results to expected results on completion of each system unit, and complete result sheets

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse and classify results

  1. Summarise and classify results, highlighting critical or urgent areas of concern, and prepare report
  2. Compare results against requirements
  3. Notify operations of test completion
  4. Log attendees’ details or comments and gain required signatures
  5. Schedule feedback meeting to discuss report and possible next actions with stakeholders, if necessary
  6. Ensure test reporting complies with documentation and reporting standards
Summarise and classify results, highlighting critical or urgent areas of concern, and prepare report

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Compare results against requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Notify operations of test completion

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Log attendees’ details or comments and gain required signatures

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Schedule feedback meeting to discuss report and possible next actions with stakeholders, if necessary

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Ensure test reporting complies with documentation and reporting standards

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Prepare for test

1.1 Prepare test environment

1.2 Determine software life cycle

1.3 Define test plan and appropriate test tools

1.4 Recognise and separate the system into runnable modules that mirror live scenarios

1.5 Gather and prepare logs and result sheets

1.6 Notify operations of scheduled test to ensure preparedness and understanding of implications for operations

1.7 Test scripts for online test or test run for batch test

1.8 Conduct walk-through to review expected results against acceptance criteria and system requirements documentation

2. Conduct test

2.1 Run test scripts and document results according to test and acceptance processes

2.2 Perform required quality benchmarks or comparisons for acceptance testing

2.3 Adopt organisation and industry standards

2.4 Compare actual results to expected results on completion of each system unit, and complete result sheets

3. Analyse and classify results

3.1 Summarise and classify results, highlighting critical or urgent areas of concern, and prepare report

3.2 Compare results against requirements

3.3 Notify operations of test completion

3.4 Log attendees’ details or comments and gain required signatures

3.5 Schedule feedback meeting to discuss report and possible next actions with stakeholders, if necessary

3.6 Ensure test reporting complies with documentation and reporting standards

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Prepare for test

1.1 Prepare test environment

1.2 Determine software life cycle

1.3 Define test plan and appropriate test tools

1.4 Recognise and separate the system into runnable modules that mirror live scenarios

1.5 Gather and prepare logs and result sheets

1.6 Notify operations of scheduled test to ensure preparedness and understanding of implications for operations

1.7 Test scripts for online test or test run for batch test

1.8 Conduct walk-through to review expected results against acceptance criteria and system requirements documentation

2. Conduct test

2.1 Run test scripts and document results according to test and acceptance processes

2.2 Perform required quality benchmarks or comparisons for acceptance testing

2.3 Adopt organisation and industry standards

2.4 Compare actual results to expected results on completion of each system unit, and complete result sheets

3. Analyse and classify results

3.1 Summarise and classify results, highlighting critical or urgent areas of concern, and prepare report

3.2 Compare results against requirements

3.3 Notify operations of test completion

3.4 Log attendees’ details or comments and gain required signatures

3.5 Schedule feedback meeting to discuss report and possible next actions with stakeholders, if necessary

3.6 Ensure test reporting complies with documentation and reporting standards

Evidence of the ability to:

test the operation and consistency of the total system prior to delivery according to system requirements, including testing:

performance

security

configuration sensitivity

start-up and recovery from failure modes

analyse test results

prepare reports in compliance with documentation and reporting standards.

Note: Evidence must be provided on at least TWO occasions or systems.

To complete the unit requirements safely and effectively, the individual must:

compare and contrast the key features and processes of automated test tools

analyse input and output requirements

describe organisational practice and rules for preparing test

describe particular system requirements and key features

analyse underlying test data

Identify and summarise industry standards appropriate to performing system tests.